Augmented Reality Vehicle Search Assistance

ABSTRACT

Aspects described herein may allow for auto-locating a user in a parking lot and/or automatically directing a user to recommended inventory. For example, a customer may capture an image of a vehicle, or a marker associated with a vehicle, in a parking lot. The image may be processed locally or at a server. A vehicle may be identified based on analysis of the image. Further, information regarding the user may be processed to determine another vehicle appropriate for a recommendation. For example, a prompt on a mobile device may suggest a popular model similar to the vehicle being viewed. The system may then provide directions (e.g., augmented reality directions) to the user to direct the user to the vehicle.

CROSS-REFERENCE TO RELATED APPLICATIONS

The instant application is a continuation of and claims priority toco-pending U.S. patent application Ser. No. 17/539,713 titled “AUGMENTEDREALITY VEHICLE SEARCH ASSISTANCE,” filed Dec. 1, 2021, which is acontinuation of and claims priority to U.S. patent application Ser. No.16/868,066, titled “AUGMENTED REALITY VEHICLE SEARCH ASSISTANCE,” filedMay 6, 2020, and issued as U.S. Pat. No. 11,195,226 on Dec. 7, 2021, thedisclosure of which is hereby incorporated by reference in its entirety.

FIELD OF USE

Aspects of the disclosure relate generally to electronic devices. Morespecifically, aspects of the disclosure may provide for systems andmethods for auto-locating a user in a parking lot and/or automaticallydirecting a user to recommended inventory.

BACKGROUND

Auto dealerships today may physically deploy people to parking lots andother locations to allow potential customers the ability to view andtest drive vehicles. Additionally, vehicles on a dealer lot are oftenrandomly distributed, and it may be difficult for a customer to find aphysical vehicle corresponding to an online dealership listing. Thus,the physical location, accessibility, and availability of autodealerships and their vehicles can be a problem for customers orpotential buyers who may desire to view a vehicle. Systems and methodsto better facilitate vehicle sales are needed.

SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

Aspects discussed herein may provide a computer-implemented method forauto-locating a user in a parking lot and/or automatically directing auser to recommended inventory. The method may utilize modern technologyto provide a user with access to a vehicle without the need to consultan in-person salesman, while managing inventory and vehicle access. Forexample, in at least one implementation, a mobile device may send, to aserver, authentication information associated with a user. The mobiledevice may use an image sensor to capture an image of a vehicle or aphysical marker. The mobile device may also determine locationinformation corresponding to a location of the mobile device. Thelocation information may comprise a QR code or GPS data. The server(e.g., after receiving the image and the location information) maydetermine one or more possible vehicles that correspond to the image(e.g., based on correlating the location of the mobile device with aplurality of vehicles proximate to the location). The image may beprocessed (by the mobile device or by the server) to determine if thevehicle in the image satisfies a threshold similarity with the geometryof a vehicle of one or more possible vehicles. The server may send arequest to the mobile device to confirm the identity of the vehicle, andmay receive a confirmation of the vehicle from the mobile device. Alocation of the mobile device may be updated based on confirming aproximity to the vehicle.

The server may determine, based on one or more characteristics of thevehicle, a listing of one or more additional vehicles. The listing maybe determined based on one or more characteristics of the vehicle. Oneor more preferred alternative characteristics may be determined based ondemographic information associated with the user. The plurality ofvehicles of the listing may be determined based on the plurality ofvehicles being associated with the one or more preferred alternativecharacteristics. The server may send, to the mobile device, the listing,wherein the listing may comprise one or more relative locations for eachof the one or more additional vehicles. The mobile device may displaythe listing, which may comprise one or more attributes of the vehiclesnotated in the listing, and may receive a selection of one or moreattributes and/or one or more vehicles via the mobile device. A path tothe relative locations of the one or more additional vehicles (and/orthe selected vehicles or vehicles corresponding to the attributes) fromthe location of the mobile device may be determined (e.g., by the mobiledevice, or from the server, which may send the path to the mobiledevice). The one or more relative locations may be relative to theinitial vehicle captured in the image. The server may cause display ofone or more directional indicators corresponding to the one or morerelative locations, which may be displayed on the mobile device. The oneor more directional indicators may comprise one or more directions tothe one or more additional vehicles, wherein the one or more directionalindicators may comprise a display of an indicator relative to therelative orientation of the mobile device. The location of vehicles maybe updated. For example, the server may receive additional locationinformation corresponding to the plurality of vehicles, may update adatabase with the additional location information, and may determine oneor more relative locations based on the location information. Theadditional location information may be determine based on examining oneor more images associated with the plurality of vehicles, wherein theone or more images may indicate where the plurality of vehicles areparked.

Corresponding apparatus, systems, and computer-readable media are alsowithin the scope of the disclosure.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 depicts an example of a computing device that may be used inimplementing one or more aspects of the disclosure in accordance withone or more illustrative aspects discussed herein;

FIG. 2 depicts an example environment in accordance with one or moreillustrative aspects discussed herein;

FIG. 3 depicts an example network in accordance with one or moreillustrative aspects discussed herein;

FIG. 4 depicts a flow diagram of an example method for facilitatingautomated vehicle access in a retail environment in accordance with oneor more illustrative aspects discussed herein;

FIG. 5 depicts a flow diagram of an example method for an automatedvehicle tracking system in accordance with one or more illustrativeaspects discussed herein;

FIG. 6 depicts an example system for displaying an augmented reality(AR) indicator to direct a user to a destination in accordance with oneor more illustrative aspects discussed herein;

FIG. 7 depicts a flow diagram of an example method for displaying an ARindicator to direct a user to a destination in accordance with one ormore illustrative aspects discussed herein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings, which form a part hereof, and inwhich is shown by way of illustration various embodiments in whichaspects of the disclosure may be practiced. It is to be understood thatother embodiments may be utilized and structural and functionalmodifications may be made without departing from the scope of thepresent disclosure. Aspects of the disclosure are capable of otherembodiments and of being practiced or being carried out in various ways.Also, it is to be understood that the phraseology and terminology usedherein are for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof.

By way of introduction, aspects discussed herein may relate to systems,methods, techniques, apparatuses, and non-transitory computer readablemedia for auto-locating a user in a parking lot and/or automaticallydirecting a user to recommended inventory. For example, a customer maycapture an image of a vehicle, or a marker associated with a vehicle, ina parking lot. The image may be processed locally or at a server. Usingcontext information (e.g., visual information of the vehicle, themarker, surrounding geometry, or location information associated withthe user), the vehicle may be identified (e.g., make, model, and/orfeatures). Further, information regarding the user may be processed todetermine another vehicle appropriate for a recommendation. For example,a prompt on a mobile device may suggest a popular model similar to thevehicle being viewed. The system may then provide directions (e.g.,augmented reality directions) to the user to direct the user to thevehicle. Further discussion regarding some aspects of the use ofphysical markers to identify a vehicle, and/or the use of augmentedreality directions to find a vehicle, may be found in U.S. applicationSer. No. 16/434,505, entitled “Automated System for Car Access in RetailEnvironment,” the contents of which is incorporated herein in itsentirety. As discussed further herein, this combination of features mayallow a user to identify a vehicle for purchase on a crowded andever-changing dealership lot.

Before discussing these concepts in greater detail, however, severalexamples of a computing device that may be used in implementing and/orotherwise providing various aspects of the disclosure will first bediscussed with respect to FIG. 1 .

FIG. 1 illustrates one example of a computing device 101 that may beused to implement one or more illustrative aspects discussed herein. Forexample, computing device 101 may, in some embodiments, implement one ormore aspects of the disclosure by reading and/or executing instructionsand performing one or more actions based on the instructions. In someembodiments, computing device 101 may represent, be incorporated in,and/or include various devices such as a desktop computer, a computerserver, a mobile device (e.g., a laptop computer, a tablet computer, asmart phone, any other types of mobile computing devices, and the like),and/or any other type of data processing device.

Computing device 101 may, in some embodiments, operate in a standaloneenvironment. In others, computing device 101 may operate in a networkedenvironment. As shown in FIG. 1 , various network nodes 101, 105, 107,and 109 may be interconnected via a network 103, such as the Internet.Other networks may also or alternatively be used, including privateintranets, corporate networks, LANs, wireless networks, personalnetworks (PAN), and the like. Network 103 is for illustration purposesand may be replaced with fewer or additional computer networks. A localarea network (LAN) may have one or more of any known LAN topology andmay use one or more of a variety of different protocols, such asEthernet. Devices 101, 105, 107, 109 and other devices (not shown) maybe connected to one or more of the networks via twisted pair wires,coaxial cable, fiber optics, radio waves or other communication media.

As seen in FIG. 1 , computing device 101 may include a processor 111,RAM 113, ROM 115, network interface 117, input/output interfaces 119(e.g., keyboard, mouse, display, printer, etc.), and memory 121.Processor 111 may include one or more computer processing units (CPUs),graphical processing units (GPUs), and/or other processing units such asa processor adapted to perform computations associating smart keystorage devices with vehicle keys, tracking the status of vehicle keysbased on sensor data received from the smart key storage devices,generating vehicle access for a user (e.g., for a test drive), trackingvehicle locations, calculating directions to/from a vehicle, and otherfunctions. I/O 119 may include a variety of interface units and drivesfor reading, writing, displaying, and/or printing data or files. I/O 119may be coupled with a display such as display 120. Memory 121 may storesoftware for configuring computing device 101 into a special purposecomputing device in order to perform one or more of the variousfunctions discussed herein. Memory 121 may store operating systemsoftware 123 for controlling overall operation of computing device 101,control logic 125 for instructing computing device 101 to performaspects discussed herein. Furthermore, memory 121 may store variousdatabases and applications depending on the particular use, for example,user profile database 127, vehicle database 129, parking spot database131, and other applications 133 may be stored in a memory of a computingdevice used at a server system that will be described further below.Control logic 125 may be incorporated in and/or may comprise a linkingengine that updates, receives, and/or associates various informationstored in the memory 121 (e.g., user identifiers, vehicle and vehiclekey identifiers, locking information, statuses, location information,directional information, etc.). In other embodiments, computing device101 may include two or more of any and/or all of these components (e.g.,two or more processors, two or more memories, etc.) and/or othercomponents and/or subsystems not illustrated here.

Devices 105, 107, 109 may have similar or different architecture asdescribed with respect to computing device 101. Those of skill in theart will appreciate that the functionality of computing device 101 (ordevice 105, 107, 109) as described herein may be spread across multipledata processing devices, for example, to distribute processing loadacross multiple computers, to segregate transactions based on geographiclocation, user access level, quality of service (QoS), etc. For example,devices 101, 105, 107, 109, and others may operate in concert to provideparallel computing features in support of the operation of control logic125.

One or more aspects discussed herein may be embodied in computer-usableor readable data and/or computer-executable instructions, such as in oneor more program modules, executed by one or more computers or otherdevices as described herein. Generally, program modules includeroutines, programs, objects, components, data structures, etc. thatperform particular tasks or implement particular abstract data typeswhen executed by a processor in a computer or other device. The modulesmay be written in a source code programming language that issubsequently compiled for execution, or may be written in a scriptinglanguage such as (but not limited to) HTML or XML. The computerexecutable instructions may be stored on a computer readable medium suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. As will be appreciated by one of skill in the art, thefunctionality of the program modules may be combined or distributed asdesired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more aspects discussed herein, and such data structuresare contemplated within the scope of computer executable instructionsand computer-usable data described herein. Various aspects discussedherein may be embodied as a method, a computing device, a dataprocessing system, or a computer program product.

Having discussed several examples of computing devices which may be usedto implement some aspects as discussed further below, discussion willnow turn to an illustrative environment and network for test drivingvehicles with minimal human interaction.

FIG. 2 depicts an example environment 200 in accordance with one or moreillustrative aspects discussed herein. In at least one aspect, a user222, via a mobile device 224, may be able to view a vehicle 208 withlimited human interaction. For example, the user 222 may send a requestto view and/or test drive a desired vehicle 208. In various embodiments,“test drive” may be further used to refer to the act of driving avehicle in order to test the vehicle before a rental, lease, or purchaseagreement. The request may be inputted into an application running onmobile device 224 and may be sent to a remote or local server 202. Theuser 222 may be given instructions that the desired vehicle is parked ata specific parking spot 206C. Also or alternatively, the user 222 mayvisually survey various vehicles parked in a plurality of parking spots206A-206C (other vehicles not shown), and choose to view and/or testdrive one of the vehicles (e.g., vehicle 208). The user 222 may be giveninstruction, e.g., via an application running on mobile device 224 andhosted and/or managed by a server 202, to access a vehicle key 218 forthe desired vehicle 208 from a vehicle key storage device 204C. Smartkey storage devices 204A-204C may be located adjacent to and/or in frontof parking spots 206A-206C. The smart key storage device may comprise acompartment, container, storage facility, or similar apparatus (“storagecompartment”) having an entry that can be locked or unlocked. The entrybe a door, lid, chute, and/or other panel (“storage door”) that could beelectronically locked or unlocked to deny or allow access to contentswithin the storage compartment. A key, key fob, remote, or electronicdevice for accessing a vehicle (“vehicle key”) may be a content that canbe stored in the storage compartment of the smart key storage device.While referred to as a “vehicle key” for simplicity, it is to beunderstood that the vehicle key need not be restricted to conventionalmechanical keys but may also include electronic devices, remotes, keyfobs, and other means for accessing a vehicle.

The instructions to access a vehicle key from a specified smart keystorage device may be given by server 202. The server may also provideand/or equip the smart key storage devices 204A-204C with unlockinstructions. For example, an unlock instruction may include aninstruction to unlock a door, lid, chute, and/or other panel (“storagedoor”) to the storage compartment 220 of the smart key storage device204A-204C (e.g., in response to an unlock request signal sent by themobile device 224). The unlock request signal may be a near fieldcommunication (NFC) signal sent by the mobile device 224 to a NFCreceiver on the smart key storage device. The unlock instruction mayinclude an instruction to unlock the storage door to the storagecompartment 220 of the smart key storage device 204A-204C if the mobilephone registers and/or captures a physical marker 226A-226C (e.g., RFIDtag) on the smart key storage device. After registering or capturing thephysical marker 226A-226C, the mobile device 224 may relay a signal tothe server 202, which may inform the smart key storage device 204A-204Cto unlock. The server 202 may track the status of each smart key storagedevice 204A-204C via their respective wireless transceivers 214A-214C.

A user 222 desiring to view details of and/or test drive a vehicle 208parked in parking spot 206C may register or capture the physical marker226C of the adjacent smart key storage device 204C. An identifier (e.g.,RFID) may be captured from the physical marker 226C by a sensor (e.g.,scanner, camera, etc.) on the mobile device 224, and the sent to theserver 202. The server may then allow the smart key storage devicecorresponding to the scanned physical marker (e.g., smart key storagedevice 204C) to unlock its storage door, allowing the user 222 to accessthe vehicle key 218 that is stored in the storage compartment. Thevehicle key 218 may also have a physical marker that is detectable by akey sensor 216 in the storage compartment. In some aspects, the storagecompartment may be designed to prevent random contents from beingstored, other than vehicle keys.

The key sensor 216 may be located within the storage compartment of thesmart key storage device. The key sensor 216 may detect that the vehiclekey 218 has been removed or placed and may update the server 202 of theremoval or placement. The key sensor 216 may also detect the presence ofthe key and update the server 202 accordingly. Information regarding avehicle key's placement, removal, or presence in a smart key storagedevice may be used by the server to update the status of the smart keystorage device or the vehicle key, or form an association between thesmart key storage device and the vehicle key. Furthermore, the keysensor may be capable of detecting a physical marker on the vehicle key.

Thus, the key sensor 216 may comprise one or more sensors that candetect motion and/or proximity, or can capture an image (e.g., to detecta physical marker). For example, the key sensor 216 may be a proximitysensor that emits an electromagnetic field or beam, or an ultrasoundfield or beam, on to the storage compartment and detect changes in thefield or return signal. The presence of a vehicle key 218 may cause thesensor to detect a significant change in the field or return signal. Inanother example, the key sensor 216 may comprise a motion sensor thatuses changes in image capturing to detect a removal or placement of avehicle key. Furthermore, the key sensor 216 may capture an image of thevehicle key and detect a physical marker from the captured image.

As described above, in some implementations, a physical marker may belocated on the smart key storage device, the vehicle key, the vehicle,and/or near a parking space. The physical marker may be stationary(e.g., a sticker having a fixed barcode) or dynamic (e.g., an electronicdisplay, such as an e-ink display, configured to display a barcode). Adynamic physical marker may be updated or changed, e.g., by the server202.

In at least another illustrative aspect, a vehicle 208 may be able todetermine the relative location of a parking spot (e.g., parking spot206C). The vehicle 208 may comprise an image sensor. For example, animage sensor may be present in an autonomous or semi-autonomous drivingsystem, such as a lane-monitoring system installed on the front of thevehicle. In another example, an image sensor may be a mobile unitinstalled in the vehicle, such as camera module adhered to a windshield(e.g., a dash cam). In yet another example, an image sensor may be amobile device, such as a phone, that is tethered to the vehicle.Physical markers 212A-212C may be installed at parking spot systems at,adjacent to, or associated with each parking spot 206A-206C. One or moreimage sensors may scan, read, or capture data from the physical markers212A-212C. The image sensors may be located within a vehicle that can beparked in the corresponding parking spot, or may be located within themobile device 224. In order to allow a vehicle's image sensor to scan,read, or capture data from physical markers 212A-212C with ease, thephysical markers 212A-212C may be appropriately positioned to face thevehicle, e.g., via stands 210A-210C. A location sensor (not shown) inthe parking spot system may transmit locational information of theparking spot so that the user 222 can be informed of the location of theuser's vehicle 208.

In at least another illustrative aspect, a user 222 may be able tolocate and obtain directions to the user's vehicle 208. The server 202may authenticate the user 222 via the user's mobile device 222, and/ormay determine a vehicle 208 associated with the user 222. The server mayobtain the vehicle's location, e.g., from a location sensor. The server202 may guide the user 222 using an augmented reality (AR) applicationon the user's mobile device 224.

In at least another illustrative aspect, a user 222 may be able to viewinformation regarding the requested vehicle 208 via the user's mobiledevice 224. The server 202 may authenticate the user 222 via the user'smobile device 224 and determine a vehicle 208 associated with a requestby the user 222. The association may be based on data obtained by themobile device 224 from image data associated with the vehicle 208 (e.g.,based on the geometry of the vehicle, a physical marker associated withthe vehicle, the location of the user 222, etc.). Also or alternatively,the server may track the vehicle and/or the user 222, e.g., fromlocation sensors in the mobile device 224 and/or the vehicle 208. Forexample, a user 222 may request to view a vehicle using the mobiledevice 224. The server 202 may unlock the vehicle 208 (e.g., forinspection of an interior) after confirming that the location of themobile device 224 is within a proximity of the vehicle 208 and/orparking spot 206C.

FIG. 3 depicts an example network 300 in accordance with one or moreillustrative aspects discussed herein. Each component or subcomponentshown in FIG. 3 may be implemented in hardware, software, or acombination of the two. Additionally, each component or subcomponent mayinclude a computing device (or system) having some or all of thestructural components described above for computing device 101. At ahigh level, the network 300 may include, for example, one or more mobiledevices (e.g., mobile device 302), one or more parking spot systems(e.g., parking spot system 318), one or more vehicle systems (e.g.,vehicle 334), and one or more server systems (e.g., server system 352).The mobile device 302 (e.g., a “user device”) may comprise a mobilephone (e.g., smartphone), personal computer, tablet computer, laptop, orthe like, which may include at least some of the features describedherein. The mobile device 302 may belong to a user seeking to utilizesystems and methods described herein, and may be used to send requeststo and/or receive notifications from server system 352, e.g., via anapplication and/or program hosted, managed, and/or otherwise controlledby the server system 352. For example, the mobile device 302 may be usedto request information about and/or access to a vehicle, such as thevehicle associated with vehicle system 334. The mobile device 302 may bea computing device distinct from the parking spot system 318, or theserver system 352.

According to some aspects of the disclosure described herein, the mobiledevice 302 may comprise one or more components or features describedbelow. Through a communications interface 312, the mobile device may beable to form wired and/or wireless data connections with other computingsystems and devices, such as the one or more components of the parkingspot system 318, the vehicle 334, and the server system 352, asdescribed further below, via an internet and/or other telecommunicationsnetwork (e.g., network 390). The mobile device 302 may include varioussensors 304 configured to capture physical data (e.g., from physicalmarkers); collect locational, geographical, and/or movement information;and/or transmit data. For example, the mobile device 302 may comprise abuilt-in or connected image sensor 308 (e.g., a camera, a scanner, etc.)that may scan and/or generate image and/or video data. A user mayoperate image sensor 308 to capture image and/or video data including aphysical marker associated with parking sport system 318 and/or vehiclesystem 334, for example, a linear barcode, a matrix (2D) barcode (e.g.,Aztec Code, augmented reality (AR) code, data matrix, quick response(QR) code, etc.) associated with a device and/or system. The sensors 304within the mobile device may further include one or more orientationsensors 310 (e.g., gyrometer, solid-state gyroscope, accelerometer,compass, etc.) to measure a measure acceleration, direction, and/orrotation of the vehicle. Furthermore, the sensors 304 may include alocation sensor 306 (e.g., global positioning system (GPS)) to determinea location of the mobile device. Other types of sensors may also bedownloaded as applications 316. The mobile device 302 may also storeuser-specific identifying information within its memory (not shown),which can be accessed by or sent to the server 352, e.g., as metadata.

The user interface 314 may be a display coupled with input devices(e.g., keyboard, type pad, touch screen, mouse, buttons, icons,microphone, sensors, etc.) that allows a user to send requests, inputinformation and/or view information. For example, the user interface 314may allow a user to send a request to the server system 352 to testdrive a vehicle near the user. The user interface 314 may then displayinstructions to the user to interact with a smart key storage device toaccess a vehicle key to test drive the vehicle. The mobile device 302may also run programs or applications 316 on a user interface 314. Oneapplication or program may enable a user to use the systems and methodsdescribed herein to test drive a vehicle with limited human interaction.The application or program may be provided to the user device or hostedby server 352 (e.g., via an application program interface (API) 366). Insome implementations, the mobile device 302 may include one or moresubcomponents of computing device 101, shown in FIG. 1 .

The parking spot system 318 may include one or more devices, computingsystems, or sensors at, adjacent to, or associated with a parking spotof a vehicle. The parking spot system 318 may include one or more of thefeatures and components described below. The parking spot system 318 mayinclude various sensors 320 configured to capture physical data (e.g.,from a physical marker on mobile device 302 or on a vehicle parked in avehicle spot at, adjacent to, or associated with the parking spot system318); collect locational or geographical information (e.g., via locationsensor 324); track the presence, absence, removal, or replacement ofkeys (e.g., via key sensor 322); and/or transmit sensor data. Forexample, the parking spot system 318 may include a built-in or affixedimage sensor 326 (e.g., a camera, a scanner, etc.) that may scan and/orgenerate image and/or video data. These data may include, for example, alinear barcode, a matrix (2D) barcode (e.g., QR code, AR code, etc.).Thus, a user may present a mobile device with a downloaded or displayedphysical marker to the image sensor 326 so that the image sensor cancapture or register a requisite image or video data (e.g., linearbarcode, matrix barcode, etc.). In some implementations, as a vehicle isbeing parked into a parking spot at, adjacent to, or otherwiseassociated with the parking spot system 318, the image sensor 326 may beable to detect a physical marker on the vehicle.

The parking spot system 318 may comprise a smart key storage device 328,and a communications interface 330 to establish wireless, wired, ornetwork connections with one or more other systems (e.g., the mobiledevice 302, the server system 352, the vehicle systems 334, etc.) Thesmart key storage device 328 may be a compartment, container, storagefacility, or similar apparatus (“storage compartment”) having an entrythat can be locked or unlocked. The entry may be a door, lid, chute,and/or other panel (“storage door”) that could be electronically lockedor unlocked to deny or allow access to contents within the storagecompartment. A key, key fob, remote, or electronic device for accessinga vehicle (“vehicle key”) may be a content that can be stored in thestorage compartment of the smart key storage device 328. As describedabove, it is to be understood that the vehicle key need not berestricted to conventional mechanical keys but may also includeelectronic devices, remotes, key fobs, and other means for accessing avehicle. The vehicle key and the smart key storage device 328 may eachhave their own unique identifiers. For example, a first identifier maycorrespond to the smart key storage device and a second identifier maycorrespond to the vehicle key. An association between the specific smartkey storage device and a specific vehicle may be formed using theirrespective identifiers at the server system 352. The key sensor 322 maybe located within the smart key storage device 328 and may track thepresence, absence, removal, and/or replacement of the vehicle key withinthe storage compartment. The key sensor 322 may be an electronic devicethat transmits radio signals to the storage compartment to monitorwhether an object is present. Also or alternatively, the key sensor 322may be an image sensor that reads or detects an identification on avehicle key (e.g., a linear barcode, a matrix barcode, etc.). Also oralternatively, the key sensor 322 may be an RFID reader that reads ordetects radio frequency emitted by the vehicle key. Upon detection of apresence and/or replacement of a vehicle key in the storage compartment,the key sensor 322 may recognize that the detected vehicle key is acorrect vehicle key via a determination that an identification of thevehicle key (e.g., an RFID, linear barcode, matrix barcode, etc.)matches an identification of the vehicle key that is associated with thesmart key storage device 318. The determination of whether the detectedvehicle key is the correct vehicle key, and the association may occur atthe server system 352. Sensor data from the key sensor 318 may thus besent to the server system 352 via a network 390.

The parking spot system 318 may further comprise a physical marker 332.The physical marker 332 may be a linear barcode (e.g., universal productcode (UPC)), matrix barcode (e.g., QR code, AR code, etc.), or an RFIDtag. The physical marker 332 may be utilized by a scanner, image sensor,and/or reader, e.g., on the mobile device 302 or the vehicle. Forexample, a user seeking to obtain a vehicle key from the smart keystorage device 328 may be instructed to present scan, capture, and/orregister the physical marker 332 (e.g., a QR code) using an image sensor308 of the mobile device 302. The image sensor may be used by anapplication 316.

The vehicle 334 may include one or more devices, computing systems,circuitry or sensors that are interior to, exterior to, or otherwiseassociated with a vehicle. The parking spot system 318 may include oneor more of the features and components described below, according tosome aspects of the present disclosure. For example, the vehicle 334 mayinclude various sensors 334 configured to capture a state of the vehicle(e.g., parking sensor 346); collect locational or geographicalinformation (e.g., location sensor 348); scan, read, or capture image orvideo (e.g., image sensor 350); and/or transmit sensor data. Forexample, a parking sensor 346 may detect when a vehicle is being parkedor is in a “parked” state. The parking sensor 346 may be anaccelerometer that recognizes a vehicle parking based on a change inacceleration of a component of the vehicle (e.g., that the vehicle hasceased movement for a threshold time). Also or alternatively, theparking sensor 346 may be an image sensor reading when an indicator forparking is turned on, or a sensor (e.g., an ODBII-compatible sensor)that detects a change in a mechanical structure of the vehicle (e.g.,brakes, clutch, etc.) as the vehicle is parked. The vehicle 334 mayinclude a location sensor (e.g., a global positioning service (GPS)) tocapture and present a location of the vehicle. In some implementations,the vehicle 334 may include an image sensor 350 that scans, reads, orcaptures a physical marker at a parking spot (e.g., physical marker 332of the parking spot system 318), as the vehicle parks or approaches theparking spot. From data captured from the physical marker 332, the imagesensor 350 may allow the server system 352 to determine the locationalinformation of the parking spot. For example, the server system 352 mayhave a list of known locations associated with identifiers and otherdata captured by sensors from physical markers. As discussed herein,there may be a physical marker located on one or more of the parkingspot system (e.g., physical marker 332), the vehicle key, or the vehiclesystem 334 (e.g., physical marker 342), according to some aspects of thepresent disclosure.

Additionally or alternatively, the vehicle may include a physicalmarker, e.g., physical marker 342, which may comprise a linear barcode,matrix barcode, RFID tag, etc. Thus, in some aspects, a user could relyon an image sensor 326 of the parking spot system 318 to scan a physicalmarker on the vehicle (e.g., physical marker 342), rather than use themobile device's image sensor 308 to scan a physical marker 332 of theparking spot system 318. Thus, the parking spot system 318 may comprisean image sensor 326 that may scan the physical marker 342 to determineif/where the vehicle 334 is parked. This may be an alternative to thevehicle 334 recording the physical marker 332, such as may be describedin FIG. 6 . The physical marker may be stationary (e.g., a stickerhaving a fixed barcode) or dynamic (e.g., an electronic displayconfigured to display a barcode). For example, a dynamic physical markermay be updated or changed by the vehicle 334 and/or by one or moreexternal systems (e.g., mobile device 302, parking spot system 318,server system 352, etc.). In some implementations, a sensor 320 from theparking spot system 318 (e.g., image sensor 326) or a sensor 304 fromthe mobile device 302 may scan, read, and/or capture data from physicalmarker 342. For example, an electronic sensor from the mobile device 302may capture data from the physical marker 342 on the vehicle, and causethe vehicle to unlock or lock. The vehicle 334 may include a lockingsystem 340 that can electronically and/or mechanically cause the vehicleto unlock or lock based on signals received, e.g., from the mobiledevice 302.

The vehicle 334 may also include a user interface to allow a user (e.g.,a test driver such as user 222) to view sensor data (e.g., location,vehicle state, parking spot information, etc.) received from theabove-described sensors, or communicate with external systems. Thevehicle 334 may send information to or receive information from othersystems (e.g., the mobile device 302, the parking spot system 318, theserver system 352, etc.) over a network 390, via communicationsinterface 336. The communications interface 336 may comprise a wirelesscommunications interface, such as a cellular connection (e.g., LTE, 5G),a Wi-Fi connection (e.g., Wi-Fi 5 or Wi-Fi 6), or a Bluetooth tether toa mobile device 302.

The server system 352 may comprise one or more remote, local, and/orconnected computing systems or servers managing one or more functions ofthe above-described systems (e.g., the mobile device 302, the parkingspot system 318, the vehicle 334, etc.) to facilitate methods andsystems described herein. For example, in some implementations, server352 may be connected to the parking spot system 318. At a high level,the server system may comprise one or more databases 354, applicationprogram interfaces (APIs) 366, a linking engine 376, an update interface378, and a communications interface 380. The update interface 378 andlinking engine 376 may form a database management application, software,or plug-in that may be used to perform create, read, update, or destroy(CRUD) functions with respect to data stored in the one or moredatabases 354. For example, the linking engine 376 may be used to formassociations or link suitable data from different databases together,and/or to create new data based on associations or linkages. The updateinterface 378 may be used to update databases (e.g., by adding ordeleting) data stored in the one or more databases 354 based oninstructions from other parts of the server system 352 (e.g., computerreadable instructions stored in memory of an API) or informationreceived from one or more external systems (e.g., the mobile device 302,the parking spot system 318, the vehicle 334, etc.). The server system352 may send information to or receive information from the externalsystems over a network 390 via communications interface 336.

The server system 352 may include one or more databases described below.For example, the server system 352 may include a database of userprofiles 356, which store identifying or biographical informationpertaining to a user. The user profile may be based on or associatedwith an identifier of a mobile device of the user (e.g., mobile number,device identifier, etc.).

Also or additionally, the sever system 352 may include a database ofknown parking spots 362, e.g., based on a geographic region. Forexample, the database of parking spots 362 may store identifiers ofparking spots within a predetermined distance from a designated addressor location. The address or location may be based on the location of auser, which can be found using a location sensor, e.g., of the mobiledevice 302 or of the vehicle system 334. Thus, a database of parkingspots 362 for the example environment illustrated in FIG. 2 may includeidentifiers of parking spots 206A-206C.

Also or additionally, sever system 352 may include a database of vehicleprofiles 358. The vehicle profiles may identify vehicles, e.g., byvehicle identification numbers, license plate numbers, and/or or othervehicle descriptors. In some examples, a vehicle may be identified basedon an identifier of its vehicle key (e.g., a vehicle key ID). The listof vehicles may depend on the systems and methods for which the server352 is being utilized. For example, the vehicle profiles database 358may identify vehicles that one or more users may test drive with limitedhuman interaction based on systems and methods described herein. In someimplementations, the server 352 may include a database for vehicle keyIDs 360, and this database may be a part of the database of vehicleprofiles 358 (as shown) or as a separate database. The database ofvehicle key IDs 360 may list vehicle key IDs for vehicles, e.g., that auser can test drive with minimal human interaction. Furthermore, thedatabase may list a status for each vehicle key, e.g., whether thevehicle key is stored within the smart key storage device, whether ithas been removed by a user, etc. The vehicle profiles database 358 maycomprise various characteristics of the vehicles. For example, thevehicles profile database 358 may store make information, modelinformation, vehicle class (e.g., 4-door sedan, minivan, sports coupe,heavy-duty truck), color, seat arrangement, feature package, mileage,model year, price, or any other such information that might be relevantto a purchaser (e.g., wheel size, sunroof, etc.).

Also or additionally, the sever system 352 may include a database forsmart key storage devices 364, which may identify smart key storagedevices by unique identifiers. The list of smart key storage devices maybe based on a geographic region, or may be independent of its geographiclocation. For example, the identifiers for the smart key storage devicesmay be manually stored, and the smart key storage devices may be trackedover a network 390. The database for the smart key storage devices 364may indicate a status for each smart key storage device, e.g., whether avehicle key is stored, whether the vehicle key is correct, whether thestorage door is open.

The server system 352 may include one or more APIs described below. Theserver system 352 may include, e.g., an API for an application forunlocking vehicles using a mobile device (e.g., vehicle unlock API 368),an API for an application for tracking a parking location using aparking sensor (e.g., parking location API 370), an API for anapplication for finding a vehicle using a mobile device (e.g., vehiclefinder API 372), and/or an API for an application for test driving avehicle with minimal human interaction using a smart key storage device(e.g., smart key storage API 374).

FIG. 4 illustrates an example method for facilitating automated vehicleaccess in a retail environment. The method may utilize modern technologyto provide a user with access to a vehicle (e.g., vehicle system 334)without the need for an in-person salesman, while managing inventory andvehicle access. Modern vehicles may employ systems (e.g., vehicle system334) that provide electronic access to vehicles (e.g., access to aninterior using locking system 340). By identifying a user that isauthorized to access the vehicle, and by confirming that the user is inproximity to the vehicle, a server (e.g., server system 352) may allow auser to find a vehicle, access the vehicle (e.g., send a command tounlock the vehicle so that the user can inspect a vehicle or go for atest drive), see information about the vehicle, and/or find similarvehicles. The server may facilitate a user identifying a vehicle,accessing the vehicle, and identifying further vehicles as describedherein. An application (e.g., application 316) of a mobile device (e.g.,mobile device 302) may facilitate a user accessing the vehicle, and mayprovide feedback regarding the test drive to the server.

At step 405, the system may authenticate a user (e.g., a user 222). Theuser may be a user who wishes to view a vehicle (e.g., a vehicle 208,which may employ vehicle systems 334) for purchase. For example, theuser may have entered a car lot, and may be looking at one or morevehicles to purchase. The user may access an application (e.g.,application 316) to obtain a list of available vehicles for lease orpurchase. The application may obtain the list from the server, whichsupply a list of inventory within a predetermined proximity of themobile device. Authentication information (e.g., a password, afingerprint, or any other information that may be used to verify theidentity of the user) may be received by a mobile device, processed, andsent to the server.

At step 410, the system may determine permissions for the user. Forexample, the server may comprise user profile information associatedwith the user (e.g., user profiles 356). The user profile informationmay indicate information for the user such as credit worthiness,purchasing power, criminal history, or other such information that maybe used to determine if the user is qualified for a vehicle. In someinstances, the user may be pre-qualified, and a notice ofpre-qualification may be sent to the user (e.g., in an emailadvertisement) to come look at a vehicle. Permissions for the user maybe determined for multiple vehicles (e.g., a class of vehicles).Permissions may be determined as needed (e.g., determined for aparticular vehicle after step 525).

At step 415, the system may capture image data indicating a vehicle(e.g., vehicle 334). A mobile device (e.g., mobile device 302) maycapture (e.g., using an image sensor 308) image data of a vehicle, orimage data of a physical marker (e.g., physical marker 332)corresponding to the vehicle. The physical marker may comprise a matrixbarcode (e.g., QR code, AR code, etc.), as discussed above. The mobiledevice may display a prompt to a user to take an image of the matrixbarcode. A user may input a code (e.g., an alphanumeric code written onthe physical marker, such as a dealer window decal on a vehicle) on themobile device using a user interface (e.g., user interface 314). Themobile device may capture image data of the vehicle itself (e.g., one ormore images of the vehicle, which may be used to determine the vehicle).

At step 420, the system may determine a location of the user. A locationsensor (e.g., location sensor 306 of a mobile device 302) may determinea location and transmit the location to the server. Location informationcan be determined via context or through a determined location. Forexample, location information may comprise image data (e.g., image datadepicting a vehicle or physical marker at a known location), referentiallocation data (e.g., coordinates or a parking space number), GPSinformation for processing, or any other such information. In someinstances, there may be security concerns with remote access. Forexample, a user could be a teenager who is too young to test drive avehicle. In another example, a malicious person could utilize stolencredentials to allow access to a vehicle from a foreign country. Thus,it may be advantageous to confirm a proximity between the user (e.g.,using a recently authenticated mobile device 302) and the vehicle (e.g.,before a user is allowed to unlock a vehicle and view the interior). Thesystem may determine a threshold proximity between the mobile device andthe vehicle before allowing the vehicle to unlock. The location of theuser may also be used to confirm that the intended vehicle is to beunlocked (e.g., by compiling a list of nearby vehicles to becross-referenced against an image of a vehicle).

At step 425, the system may process the image data to determine thevehicle. The mobile device may process data locally, and/or the mobiledevice may transmit data to the server to be processed remotely. Themobile device may take one or more images of the vehicle, which may beused (e.g., by the mobile device 302 or the server 352) to determine thevehicle via image processing. For example, the system may determine avehicle based on identifying the geometry or an image likeness above athreshold corresponding to the vehicle, such as by using machinelearning to compare the depicted vehicle to a database of knownvehicles. For example, a make, model, color, trim, and/or year of thevehicle may be determined using image processing. The one or more imagesof the vehicle could be cross-referenced with location information todetermine the vehicle. For example, the image of the vehicle may becompared only with vehicles within a threshold proximity of thedetermined location of the user. An image of a physical marker couldalso be processed to determine an indicator that may correspond to anentry for the vehicle in a database (e.g., vehicle profiles 358). Forexample, the mobile device may detect a QR code, transmit an identifierbased on the QR code to the server, and the server may determine adatabase entry indicating a particular vehicle assigned to theidentifier. A physical marker may be associated with a parking spot(e.g., one of parking spots 206A-206C), and the system may record whatvehicle is in that parking spot. In some instances, the user may be ableto confirm, using the mobile device, that the correct vehicle has beenselected, and/or update the system with what vehicle is present if thereis an error. In some instances, a combination of the above (e.g., aphysical marker correlated with a location of the user) could be used toconfirm the identity of the vehicle (e.g., that the vehicle at thephysical marker is within a threshold proximity to the location of theuser).

In some instances, the user may be prompted to confirm the identity ofthe vehicle. Multiple vehicles may exist that are within a thresholdsimilarity to the vehicle depicted in an image and/or are within athreshold proximity to a user. For example, a lot may have multiplewhite SUVs of a given model, and though they may differ in model year orother features they may look too similar to distinguish in an image. Theuser may be prompted with a list of vehicles in order to identify whatthe vehicle is. For example, the listing may indicate parking spacesassociated with the vehicles, feature information (e.g., a model yearthat can be cross-referenced with a dealer sticker on a window), licenseplate information, or other such information that may be used to confirmthe vehicle. In some instances, after receiving the confirmation, thelocation of the user device may also be confirmed (e.g., GPS informationmay only indicate that a phone is within a wide radius in a lot, but thevehicle confirmation may identify that the user is in a particularlocation relative to the vehicle). This may have the advantage ofproviding a more precise location and/or orientation, which may be usedfor providing more accurate directions (e.g., as discussed below in FIG.6 and/or FIG. 7 ).

In some instances, a parking spot system (e.g., parking spot system 318)may capture image data. The mobile device may display an image, such asa QR code or barcode. A user may hold the mobile device up to an imagesensor (e.g., image sensor 326), so that the parking spot system maydetect the image. If the parking spot system scans an image of themobile device, the server may determine a user associated with themobile device, and determine whether to grant access to a vehicle knownto be associated with physical marker (e.g., consistent with the systemsand methods described herein). For example, a vehicle may be stored at aparking spot, and by scanning an image (e.g., a mobile device scanning aphysical marker, or a camera at the parking spot scanning a marker onthe mobile device), the system may determine that the user is at alocation associated with that particular vehicle.

In some instances, the system may receive a request for a vehiclewithout first receiving an image of a vehicle. For example, the user mayindicate one or more characteristics (e.g., preferences), such as makeof vehicle, model of vehicle, year of vehicle, mileage of vehicle, colorof vehicle, trim of vehicle, price of vehicle, location of vehicle ordealership (which may be an area, such as a radius around a location orzip code), type of vehicle (e.g., SUV, crossover, sedan), attributes(e.g., number of seats, number of doors, leather seats, heated seats,trim color), or any other such characteristic. The vehicle may beidentified to the user based on the characteristics. For example, theserver may identify one or more options of vehicles corresponding to thecharacteristics using a search. The user may select the vehicle fromthose options. The server may then indicate where the vehicle is on thelot using a parking space number, or using augmented reality (AR)indicators as discussed herein. For example, a user may requestinformation regarding the vehicle and/or access to the vehicle. Arequest may be received at the mobile device, and may be transmitted tothe server. The request may be received using a user interface, such asa website, application, or other such interface. After receiving therequest, the system may direct the user to the vehicle, such as bydisplaying directions as discussed in FIG. 6 and/or FIG. 7 .

The system may sort inventory based characteristics. The server mayretrieve an inventory list from the inventory management database (e.g.,database 354). The inventory list may indicate what vehicles areavailable at one or more dealer sites, and may also indicate when thevehicles are available (e.g., if a vehicle is unavailable due to a testdrive, maintenance, cleaning, etc.). The server may process theinventory list based on the characteristics (e.g., to be sorting orformatting vehicles based on the user preferences). Further, vehiclerecommendations may be generated, for example, using demographicinformation associated with the mobile device. The recommendations maybe determined by the server based on user profile information for a userknown to be associated with the mobile device. For example, a minivan ina particular price range may be recommended based on a user having aparticular income and multiple children. In some instances, such as if adealer has too many test drives assigned for a given day, the system maynot allow a test drive to be scheduled on that day.

At step 430, the system may allow access to the vehicle. In someinstances, the user may be permitted to access an information sheetcorresponding to the vehicle. For example, the mobile device may displaya list of attributes and/or characteristics of the vehicle to the user(e.g., car features and associated pricing information). If the systemdetermines that the user is permitted to unlock the vehicle and/or is inproximity to the vehicle, the system may send a command to unlock thevehicle. The server may utilize a vehicle unlock interface (e.g., API368) to send an unlock command (e.g., wirelessly or via a wiredconnection from communications interface 380 to communications interface336) to a locking system (e.g., a locking system 340 of a vehicle 334).The vehicle may unlock in response to the command In some instances, thelocking system may be a locking system standard to that vehicle. Inother instances, the locking system may be an aftermarket systeminstalled on the vehicle. In some embodiments, the locking system mayenable operation of the vehicle, such as by starting a vehicle andallowing it to be driven. In other instances, the locking system mayunlock a vehicle and provide access to a key fob needed to start thevehicle. In yet other instances, the locking system may work inconjunction with other systems. For example, the locking system mayprovide the means of accessing the vehicle, but a smart key storagedevice (e.g., smart key storage device 364) for starting the vehicle maybe inside or outside the vehicle, and may be accessed according tosystems and methods described herein in order to access a key to startthe vehicle.

At step 435, the system may detect the start of a test drive. The systemmay detect the start of the test drive based on movement informationfrom the mobile device, such as by using information from an orientationsensor (e.g., orientation sensor 310) or a location sensor (e.g.,location sensor 306). The system may detect the start of the test drivebased on detecting a car has gone into drive using a parking sensor(e.g., parking sensor 346). The system may detect the start of the testdrive based on detecting that the vehicle is in motion by followinglocation information from the location sensor. The system may detect thestart of a test drive based on a connection between two or morecommunication interfaces (e.g., between the communications interface 312and the communications interface 336). For example, an application(e.g., application 316) of the mobile device may automatically triggeran attempted wireless connection (e.g., Bluetooth) to the vehicle when atest drive has been authorized. If a connection is connected, this mayindicate that the mobile device is in close proximity to the vehicle. Insome instances, the system may use location information to determine atest drive is within parameters. For example, the system may limit thenumber of miles driven, limit the amount of time driven, confirm theuser is driving the vehicle based on a proximity, confirm the vehiclestays within a certain proximity of a lot, and/or track that the testdrive is safe for the vehicle.

At step 440, the system may detect that a vehicle has parked. The systemmay detect the end of the test drive based on movement information fromthe mobile device, such by using information from an orientation sensor(e.g., orientation sensor 310) or a location sensor (e.g., locationsensor 306). For example, the system may determine that the mobiledevice has ceased high-speed motion after a period of time. In anotherexample, the user interface of the mobile device may comprise a promptfor the user to indicate that the test drive has ended (e.g., a promptmay be displayed after the mobile device ceases high speed motion for aset period of time). The system may detect the end of the test drivebased on detecting a car has parked using the parking sensor. Forexample, the system may detect that the vehicle has been shifted intopark. In another example, the system may use an image sensor to detect aphysical marker indicative of a parking space, and/or to detect a gearshift indicator signaling “park.” The system may detect that the testdrive has ended based on a disconnection between two or morecommunications interfaces (e.g., the mobile device disconnectingBluetooth from the vehicle). The system may also verify that the testdrive has ended by confirming that the location of the mobile deviceand/or the vehicle is at the location of a designated parking facility.

In some instances, the system may permit a user to purchase the vehicleafter conducting a test drive. For example, after indicating that adrive has ended, a mobile device may prompt the user to purchase orlease the vehicle. The user may have the option to complete thetransaction on the mobile device, may be directed to a website orrepresentative to complete the transaction, and/or may be given thevehicle for an extended trial period (e.g., a 3-day trial upon receiptof a deposit). This may have the advantage of permitting a user topurchase a vehicle with little-to-no interaction with a human salesrepresentative.

At step 445, the system may record the vehicle location. Locationinformation may be derived from the location sensor (e.g., locationsensor 306 or location sensor 348). In some instances, particularizedinformation for a parking spot (e.g., a parking spot 206A-206C) may beused to determine where a vehicle is parked. The user may use the mobiledevice to record a physical marker, such as discussed in step 415, to“check in” the vehicle at a given parking spot (which may or may not bewhere the same spot from where the vehicle was retrieved, and may evenbe a different lot). In some instances, the vehicle may determine whereit is parked using an image sensor (e.g., image sensor 350) to record aphysical marker, such as using one or more systems or methods asdescribed herein.

At step 450, the system may determine additional vehiclerecommendations. The server may determine one or more available vehicleson a lot based on the characteristics. In some instances, the processingmay be performed by the server (e.g., before transmitting results to themobile device). In other instances, the mobile device may determineavailable vehicles based on an inventory list retrieved from the server.For example, there may be one or more other vehicles that are oftenviewed or purchased by someone who viewed the vehicle. The server maydetermine one or more preferred alternative characteristics to recommendbased on demographic information. For example, a consumer with childrenwho has asked to look at SUVs may also be presented with options for4-door sedans or minivans that can accommodate children. In anotherexample, the system may determine that another vehicle has a popularfeature (e.g., heated seats, sunroof, etc.) not present on the vehiclebeing viewed, and may recommend the alternative vehicle for viewing.This may have the advantage of promoting sales by presenting theconsumer with additional vehicles they might consider.

At step 455, the system may display a listing of the additional vehiclerecommendations to the user. For example, the system may cause a displayof the mobile device to display the listing of additional vehicles. Auser may make one or more selections (e.g., using a touchscreeninterface) of one or more vehicles to be viewed. The listing maycomprise a location of where the vehicles are located. For example, thelisting may provide a map with markers indicating the location of theadditional vehicles. In another example, the listing may provide parkingspot numbers (or other such index) notating the location of theadditional vehicles.

At step 460, the system may display directions to one or more of theadditional vehicles (e.g., based on the one or more selections). Forexample, the system may display directional indicators as may bediscussed in FIG. 6 and/or FIG. 7 . The system may determine an optimalroute based on the selections. For example, the system may determine ashortest path to traverse between all the vehicles (e.g., a shortesttotal path that walks the user by each selected vehicle). The system mayorganize vehicles for optimal viewing. For example, the system maydirect a user to travel between each vehicle of a first model beforemoving to another model. In another example, the system may start a userwith a more expensive model before moving to less expensive models(e.g., to promote higher sales).

Having discussed a method for facilitating access to vehicles as shownin FIG. 4 , discussion will now turn to a method for an automatedvehicle tracking system as shown in FIG. 5 .

FIG. 5 illustrates an example method for an automated vehicle trackingsystem. Modern vehicles may employ imaging systems (e.g., image sensor350). For example, an accident avoidance system and/or lane-keepingassistant system may employ one or more front-mounted cameras. Inanother example, a vehicle may employ one or more cameras to recordvideo footage of a drive for insurance purposes (e.g., a dash cam).These imaging systems may be standard to a vehicle, aftermarketcomponents for a vehicle, or may be modular units that may be movedbetween vehicles (e.g., a camera that may be mounted to a windshieldwith a suction cup). By utilizing a physical marker (e.g., physicalmarker 332) at a parking space, the vehicle may capture an image of thephysical marker to determine where the vehicle is parked. The parkinglocation may be sent to a server (e.g., server 352) and/or displayed toa user (e.g., using a mobile device, such as a mobile device 302, or avehicle, such as a vehicle 334). The user may be a user 222.

At step 505, the system may determine that a vehicle has parked. Thesystem may detect the end of the test drive based on movementinformation from the mobile device, such as an orientation sensor (e.g.,orientation sensor 310) or a location sensor (e.g., location sensor306). For example, the system may determine that the mobile device hasceased high-speed motion after a period of time. In another example, auser interface (e.g., user interface 314 of a mobile device 302) maycomprise a prompt for the user to indicate that the test drive has ended(e.g., a prompt may be displayed after the mobile device ceases highspeed motion for a set period of time). The system may detect the end ofthe test drive based on detecting a car has parked using a parkingsensor (e.g., parking sensor 346). For example, the system may detectthat the vehicle has been shifted into park. In another example, thesystem may use an image sensor (e.g., image sensor 350) to detect aphysical marker (e.g., physical marker 332) indicative of a parkingspace, and/or to detect a gear shift indicator signaling “park.” Thesystem may detect that the vehicle is parked based on a disconnectionbetween two or more communication interfaces a communications interface312 and a communications interface 336 (e.g., the mobile device 302disconnecting Bluetooth from the vehicle 334). The disconnection mayindicate that a user has left the vehicle. The system may determine thata user has left the vehicle (and that the vehicle is parked) based on alocation of the mobile device 302 moving away from the vehicle 334. Insome instance, the system may determine or confirm that a vehicle isparked based on detecting a physical marker 332 associated with aparking space, such as discussed in step 510.

At step 510, the system may capture image data indicating a parking spotfor a vehicle. An image sensor (e.g., image sensor 350) may detect animage of a physical marker (e.g., physical marker 332) indicating aparking spot. The physical marker may comprise a matrix barcode (e.g.,QR code, AR code, etc.), as discussed above. For example, the imagesensor may continuously scan (e.g., continually inspecting frames of avideo feed) for a physical marker (e.g., a QR code). In another example,the image sensor may capture one or more images when the systemdetermines that the vehicle has been parked, such as may be determinedin step 505. In yet another example, the system may use a camera todetect that a vehicle has parked in a parking space (e.g., byidentifying the geometry of the vehicle, by identifying a license plateof the vehicle, or by using one or more other methods described herein,such as a combination of the above using machine learning). The imagemay comprise a location tag in a predetermined zone of the image. Forexample, a physical marker may be placed at a specified height andlocation in a parking space, wherein the physical marker comprises alocation tag (e.g., a QR code). If a location tag corresponding to aphysical marker is detected in a predetermined zone of the image (e.g.,the far right of the image) it may not be considered (e.g., a physicalmarker on the far right of an image may indicate passing a parking spotrather than parking in it). If the location tag corresponding to thephysical marker is detected in the predetermined zone of the image(e.g., the center of the image at the specified height), this mayindicate the vehicle is parked in front of the physical marker.

In some instances, a user may manually capture the image data. A mobiledevice (e.g., mobile device 302) may capture (e.g., using an imagesensor 308), a physical marker corresponding to the vehicle (e.g.,physical marker 332). The mobile device or vehicle may comprise a promptwherein the user can request the mobile device or vehicle capture imagedata. A user may input a code (e.g., an alphanumeric code written on thephysical marker 332) using the user interface (e.g., the user interface314 or the user interface 338).

At step 515, the system may process the image data to determine aparking spot identifier. In some instances, a device capturing the imagedata (e.g., the vehicle) may process the image data and determine anidentifier from the data. For example, the vehicle may detect a QR code,and determine an identifier from the QR code. In other instances, theimage data may be transferred to another device for processing. Forexample, the vehicle may transfer image data to a server or a tetheredmobile device (which may in turn send data to the server). The parkingspot identifier (possibly along with an identifier of the vehicle) maybe transmitted to the server.

At step 520, the system may record a location of the vehicle. Afterreceiving and/or processing the parking spot identifier (and/or theidentifier of the vehicle), the server may determine a database entryfor the parking spot that corresponds to the parking spot identifier.The server may store information in the entry for the parking spot, suchas an indicator of the vehicle 334 an indicator of the mobile device,and/or a user (which may be an indication of a user profile, such as auser profile 356). The server may alternatively, or in addition, storeinformation in an entry for an associated user profile or vehicleprofile (e.g., vehicle profile 358), such as a location (e.g., GPScoordinate) for the vehicle, a parking spot for the vehicle, etc.

At step 525, the system may output location information for display. Theserver may send parking spot information (e.g., an indicator of aparking space, such as a lot level and/or spot number) to the mobiledevice or vehicle. The mobile device or vehicle may display the parkingspot information on its respective user interface (e.g., user interface314 and/or user interface 338).

In some instances, the parking spot information may be displayed inresponse to a user request. A user may be walking to a vehicle and maywish to determine where his or her vehicle is parked. For example, auser may be returning from a long flight, and wish to locate a vehiclein an airport parking deck. In another example, a user may wish tolocate a vehicle for rent, lease, or purchase in a retail lot. The usermay use the mobile device to access the parking spot information (e.g.,from the server) and display an indication of the parking spot on theuser interface. In some instances, the parking spot information may beutilized with one or more systems described herein. For example, theparking spot information may indicate a location of a vehicle for rentor purchase as described in FIG. 4 . In another example, the parkingspot information may be used in conjunction with a directional marker orAR marker to direct a user to a vehicle, such as described in FIG. 6and/or FIG. 7 .

Having discussed a method for an automated vehicle tracking system asshown in FIG. discussion will now turn to systems and methods fordisplaying one or more augmented reality directions as shown in FIG. 6and FIG. 7 .

FIG. 6 illustrates an example system for displaying an augmented reality(AR) indicator to direct a user (e.g., a user 222) to a destination. Adevice 605, which may be a mobile device 302, may be used to display(e.g., on a display screen 615) an indicator 610 that directs a user toa destination. While the device 605 is depicted as a mobile phone, thedevice 605 may be any mobile device, such as AR glasses, a tablet, etc.The destination may be any location, such as a location of a product ina store, a vehicle in a parking lot, or an exit from a building. Forexample, the destination may be the location of a vehicle, which may bereceived from a server (e.g., server 352). The device 605 may use anorientation sensor 310 and/or a location sensor 306 to determine theorientation of the indicator 610. For example, the device 605 maydetermine the relative location of a vehicle based on the location ofthe vehicle received from the server, a location of the device 605derived from location sensor 306, and/or an orientation of the device605 (e.g., a cardinal direction, angle, pitch, etc.) from an orientationsensor (e.g., orientation sensor 310).

In some instances, a physical marker 620 (e.g., QR code, AR code, etc.),which may be a physical marker 332, may be utilized to provide directionto the destination. The device 605 may scan the physical marker 620 todetermine a location of the device 605. For example, an application(e.g., application 316) may determine a location of the device 605 basedon detecting that it is in proximity to the physical marker 620. Inanother example, the application may determine the location of thedevice 605 based on identifying a vehicle 625, such as may be discussedabove in FIG. 4 . In another example, the device 605 may transmitinformation derived from the physical marker 620 to a server, which mayreturn a location of the device 605. In this manner, a confirmed and/orpredetermined location of the device 605 may be determined. For example,one or more predetermined paths may be created from the physical marker620 to one or more destinations (e.g., vehicle parking spaces for one ormore vehicles). The predetermined paths may be created manually orautomatically. Upon scanning the physical marker 620, the device 605 maybegin showing the path to the destination. The physical marker 620 mayalso be used to confirm orientation and location relative to the path.For example, a device 605 may be in an underground garage where locationinformation (e.g., GPS data) or orientation information (e.g., adirection) may be limited or unavailable. The orientation of thephysical marker 620 in real space may be known, such as knowing that thephysical marker 620 is flat against a wall running east to west at aparticular location. The device 605 may thus orient an indicator 610based upon the known relative location and/or orientation of thephysical marker 620. For example, if a parking spot is known to be onefloor above a physical marker 620, a device 605 detecting a physicalmarker 620 in a stairwell may display an indicator 610 pointing up aflight of stairs. More than one indicator 620 may be used in succession.For example, a device 605 may capture physical markers 620 at additionalvehicles along a route, each providing an indicator 610 directing a nextstep in a path. Each step of the path may direct the device 605 toanother physical marker 620 in succession, such that a user can followphysical markers until a destination is reached.

The indicator 610 may be displayed using an overlay on the displayscreen 615. The device 605 may capture image data (which may be a livevideo feed) of the environment. the indicator 610 may be overlaid ontothe image data for display in order to provide an augmented reality (AR)experience. The indicator may comprise an augmented reality direction.For example, the indicator 610 may be displayed as a two-dimensional orthree-dimensional indicator overlaid on a video feed, wherein theindicator may indicate a direction. The indicator 610 may be relative tothe environment. The device 605 may comprise an orientation sensor, suchas a solid-state gyroscope and/or orientation sensor 310. The indicator610 may be displayed based on an orientation received from theorientation sensor. For example, the indicator 610 may be adjusted inany direction to compensate for the orientation of the device. This mayhave the advantage of providing an accurate indicator 610 for a mobiledevice 605 that may be held at multiple angles. The indicator 610 may bea three-dimensional indicator 610, which may be overlaid such that theindicator 610 appears to “float” in the environment as a directionalsymbol pointing in three dimensions to a destination and/or providingthe next direction for a path. This may provide the user with an ARexperience with which the user may perceive directions relative to theirenvironment in multiple dimensions.

FIG. 7 illustrates an example method for displaying an AR indicator todirect a user (e.g., a user 222) to a destination. A device (e.g.,device 605) may display one or more AR indicators (e.g., AR indicators610) to the user, wherein each AR indicator directs a user to adestination location (e.g., via one or more directions down a path). Asystem may facilitate determining a location of the device, thedestination for the path, the path, and the one or more directions, suchas described herein.

At step 705, the system may authenticate a user. The user may be a userwho is utilizing a device (e.g., a device 605). For example, the usermay have requested directions to a parked vehicle (e.g., a vehicle 334).The user may access an application (e.g., application 316), and requestdirections to a destination using a user interface (e.g., user interface314). For example, the user may request directions to his or hervehicle. In another example, the user may request directions to avehicle for rent or purchase. In yet another example, the user mayrequest directions to a goods for sale at a retail location. In someexamples, the directions may traverse between multiple vehicles (e.g.,to a first vehicle, and then to one or more additional vehicles in asequence). Authentication information (e.g., a password, a fingerprint,or any other information that may be used to verify the identity of theuser) may be received by the device, processed, and sent to a server(e.g., server 352). The authentication information may be used toconfirm who the user is, what information is associated with the user,and/or that the user is permitted access to the directions. For example,a user profile (e.g., user profile 356) may indicate that a particularuser owns a particular vehicle located at a particular destination(e.g., a destination associated with a parking spot, such as parkingspot 362). Directions to a particular destination may be conditioned onaccess. For example, a user may be given directions only to a vehiclethey own, or to a vehicle they are permitted to rent or purchase. Insome instances, directions may be in response to a user being givenaccess. For example, a user may rent or purchase a good (e.g., avehicle) using the user interface, and the user may be supplieddirections to the good (e.g., directions to a parking spot of thevehicle) in return.

At step 710, the system may determine a location of the user. The devicemay determine a location based on feedback from a location sensor (e.g.,location sensor 306). For example, the device may determine a locationbased on GPS data. The system may, alternatively or in addition,determine a location based on a physical marker (e.g., physical marker620). The device may capture an image of the physical marker todetermine a location (e.g., as discussed in FIG. 6 ). The physicalmarker may be placed at a known location (e.g., a parking space, astairwell, a branch in a pathway, an entrance, an exit, etc.). Forexample, the physical marker may be placed on a window decal for avehicle for sale, wherein the parked location of the vehicle is known.An association between the physical marker may be stored in anapplication (e.g., application 316) and/or in a database (e.g., database354). If the device scans the physical marker, the system may determinethat the device is at the known location.

At step 715, a request may be made for a path to a destination. Thedevice may request a path to a destination. The path may be stored onthe device and/or at the server. For example, the device may transmit,to the server, a request for a path to the destination. The destinationmay be obtained via an interface of the device, such as a user interface(e.g., user interface 314). The destination may be determined accordingone or more systems or methods described herein. For example, a parkedlocation of a vehicle may be recorded as in FIG. 6 . The user mayrequest directions to the vehicle, and the server may determine thedestination based on the parked location of the vehicle. In anotherexample, the user may request to see a vehicle for purchase as in FIG. 4, and the server may determine a destination based on a parking spotsystem associated with the vehicle (e.g., parking spot system 318). Thepath may comprise multiple vehicles. For example, the path may firstdirect to a customer to a first vehicle, and then may direct a customerto an additional vehicle.

At step 720, a path to the destination may be determined. A path maycomprise one or more directions from the device to the destination. Theone or more directions may comprise one or more directional indicators(e.g., directional indicators 610). A path may be a route between thelocation of the device to the destination. The path may be determinedbased on shortest navigable distance between the device and thedestination. For example, the path may comprise a first direction toproceed to a row of vehicles in a parking lot, a second direction toturn at the row, and a third direction pointing to a destinationvehicle. The path may be partially or fully predetermined. For example,one or more physical markers may be placed around an area. Predeterminedpaths may be created to travel between the physical markers. If a deviceat a first physical marker requests a path to a destination, the systemmay determine a predetermined path from the first physical marker to asecond physical marker closest to the destination. The device may followthe path until the second physical marker, at which point the device maypoint to the destination.

At step 725, a first direction for the path may be determined. Thesystem may determine the first direction based on the location of thedevice and the path, such as may be described above regarding step 720.Paths and/or directions may be determined locally and/or remotely. Adevice may locally determine a path from the device to the destination(e.g., using a mapping application, such as Google Maps, on the device).A map of an area (e.g., a dealership lot) may be downloaded to thedevice for navigation and/or reference (e.g., as an overlay). A devicemay transmit a request for a path to a server, and the server maydetermine the path and transmit the path and/or directions to thedevice. For example, the server may receive a request for a path,determine a full path (e.g., a series of one or more directions) fromthe location of the device and the destination, and transmit the fullpath in one continuous transmission. In another example, the server mayreceive a request for a path, and transmit a first direction to thelocation. The server may then repeatedly receive updated locations fromthe device and transmit a new direction to the destination (from therespective updated location) after each location update. The device mayalso receive a plurality of directions to the destination initially, maytransmit location updates intermittently, and may rely on the initialdirections until and/or unless updated directions are received. This mayhave the advantage of assisting with communication lapses, as may happenin an underground garage.

At step 730, the first direction may be displayed. The first directionmay comprise an indicator (e.g., indicator 610) displayed on the device.The indicator may be displayed as discussed in FIG. 6 . For example, theindicator may be overlaid upon an environment to supply a firstdirection down a path and/or to a destination.

At step 735, a location update may be received. The device may determinea new location using one or more systems or methods as described herein.For example, the device may determine an updated location based on GPSdata. In another example, the device may reach a first vehicle of a listof vehicles to be viewed. In yet another example, the device mayencounter an additional physical marker, which may be an intermediarywaypoint (e.g., the end of a row of cars) used to generate an updatedlocation and send the user on to another destination. The locationupdate may be sent from the device to the server.

At step 740, a second direction for the path may be determined based onthe updated location. If the updated location is a point along a path,the second direction may comprise a second direction for the path. Forexample, the updated location may be the location of an additionalvehicle on a list of vehicles to be viewed. The updated location may bea deviation from a previously defined path, so the system determines anew path (e.g., using the updated location as the location and repeatingsteps 710 to 720). For example, a user may stop and view a car not onthe list, which may not be on the defined path. In some instances, auser may be directed to proceed down a path with multiple physicalmarkers (e.g., a plurality of physical markers 620), as discussedherein. The directions may indicate that the user should scan anadditional physical marker. When a user reaches each additional physicalmarker, he or she may be asked to scan the marker. A prompt or delay mayexist between stops on a path. For example, a customer may be directedto a second vehicle for viewing, and may have information for thatvehicle displayed. The user may have to select a prompt to indicate thatthe user is done viewing the second vehicle and wants directions to athird vehicle. The system may determine the new location based on thescan of the additional physical marker, and display a new direction fromthat additional physical marker (e.g., based on a known position of theadditional physical marker). For example, a path to a first vehicle mayhave a marker at an exit door, a marker at a sub-lot, a marker at eachrow of vehicles, and a marker at each vehicle. This may have theadvantage of allowing for straightforward directions to identifiablelandmarks or traversal points (e.g., doors or crosswalks) for a user.

At step 745, the second direction may be displayed. The second directionmay comprise an indicator (e.g., indicator 610) displayed on the device.The indicator may be displayed as discussed in FIG. 6 . For example, theindicator may be overlaid upon an environment to supply a seconddirection down a path and/or to a destination. Steps 735 to 745 may berepeated until the system determines that the device is at thedestination. The destination (e.g., a vehicle) may be indicated using anaugmented reality marker overlaid on a display such as display 615(e.g., an indicator arrow pointing to the vehicle, or a symbolrepresenting a vehicle).

One or more aspects described herein may provide automated systems fortracking, locating, and/or accessing vehicles. This may have the benefitof reducing the manpower needed to store, sell, lease, or rent vehicles,while reducing the strain on the consumer. For example, a consumer maybe able to quickly locate and access a vehicle for a test drive using amobile application, which may have the advantage of allowing a user toavoid a pushy salesperson (which may also reduce overhead for a cardealer). The system may also have the advantage of allowing a car dealeror financier track inventory and the condition of that inventory. Thismay promote more efficient sales due to reduced friction for theconsumer and reduced costs for the retailer.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A method comprising: receiving, by a computingdevice and from a mobile device, vehicle identification informationcorresponding to a location of the mobile device; determining, by thecomputing device and based on correlating the location of the mobiledevice with a plurality of vehicles proximate to the location, one ormore possible vehicles that correspond to the vehicle identificationinformation; sending, by the computing device and to the mobile device,a request for confirmation of the vehicle of the one or more possiblevehicles; receiving, by the computing device and based on a userresponse entered at the mobile device, the confirmation of the vehicle;determining, by the computing device and based on one or morecharacteristics of the confirmed vehicle, a listing of one or moreadditional vehicles different from the one or more possible vehicles;sending, by the computing device and to the mobile device, the listing,wherein the listing comprises one or more relative locations for each ofthe one or more additional vehicles, wherein the one or more relativelocations are relative to the vehicle; and causing, by the computingdevice, display of one or more direction indicators corresponding to theone or more relative locations.
 2. The method of claim 1, whereindetermining the one or more possible vehicles comprises determining theone or more possible vehicles based on determining that each vehicle ofthe one or more possible vehicles satisfies a threshold similarity withthe vehicle identification information.
 3. The method of claim 1,wherein the vehicle identification information comprises a locationidentifier, and wherein the location of the mobile device is determinedfrom the location identifier.
 4. The method of claim 1, furthercomprising: sending, to the mobile device, a request to confirm anidentity of the vehicle, wherein the request comprises an additionallisting of the one or more possible vehicles; and receiving, from themobile device, a confirmation of the vehicle.
 5. The method of claim 4,further comprising updating, after receiving the confirmation, thelocation of the mobile device by determining a proximity of the mobiledevice to the vehicle.
 6. The method of claim 1, wherein the determiningthe listing comprises: determining, based on demographic information,one or more preferred characteristics of a user of the mobile device;and determining the plurality of vehicles based on the plurality ofvehicles being associated with the one or more preferredcharacteristics.
 7. The method of claim 1, further comprising: receivingadditional location information corresponding to the plurality ofvehicles; updating a database with the additional location information;and determining the one or more relative locations based on theadditional location information.
 8. The method of claim 7, wherein theadditional location information comprises a parking image.
 9. The methodof claim 8, wherein the parking image comprises an image of a QR codecorresponding to a parking space for the one of the one or moreadditional vehicles.
 10. The method of claim 7, further comprisingdetermining, based on detecting the plurality of vehicles in an image ofa parking lot, the additional location information.
 11. A methodcomprising: determining, by a global positioning system (GPS) sensor ofa mobile device, a location of the mobile device; determining, by themobile device and based on the location, vehicle identificationinformation for a vehicle; sending, by a mobile device and to a server,the vehicle identification information; receiving, by the mobile device,from the server, and based on the vehicle identification information, aprompt to confirm an identity of the vehicle from one or more possiblevehicles; sending, by the mobile device and to the server, a response tothe prompt; receiving, by the mobile device, from the server, and basedon the prompt, a listing comprising one or more additional vehicles,wherein the listing comprises one or more attributes for each of the oneor more additional vehicles, wherein the one or more attributes compriseone or more vehicle features; receiving, by the mobile device, aselection of an attribute of the one or more attributes; sending, by themobile device and to the server, the selection; receiving, by the mobiledevice, from the server, and based on the selection, informationindicating a path from a location of the mobile device to a location ofthe one or more additional vehicles; determining, by the mobile deviceand based on the information indicating the path, one or more directionsfrom the mobile device to the one or more additional vehicles;determining, by the mobile device, and based on determining a relativeorientation of the mobile device and the one or more additionalvehicles, one or more direction indicators corresponding to the one ormore directions; and displaying, by the mobile device and based on therelative orientation, the one or more direction indicators.
 12. Themethod of claim 11, wherein the location of the mobile device isdetermined based on an image.
 13. The method of claim 11, wherein theone or more direction indicators comprise a plurality of directionindicators each relative to one of a plurality of vehicles of the one ormore additional vehicles.
 14. The method of claim 11, wherein the one ormore direction indicators comprises a directional symbol indicating arelative position of one of the one or more additional vehicles based onthe relative orientation of the mobile device.
 15. The method of claim11, wherein the relative orientation is based on feedback from asolid-state gyroscope.
 16. An apparatus comprising: a location sensor; awireless transceiver; an orientation sensor; a display screen; one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the apparatus to: determine, using thelocation sensor, a location of a apparatus; receive, using the wirelesstransceiver, from a server, and based on the location, one or morepossible vehicles that correspond to an identity of a vehicle;prompting, using the display screen, a user to identify the vehicle fromthe one or more possible vehicles; send, using the wireless transceiver,a user response to the prompt; receive, using the wireless transceiver,from the server, and based on the user response, a listing comprisingone or more additional vehicles other than the vehicle, wherein thelisting comprises one or more attributes for each of the one or moreadditional vehicles; receive, using the wireless transceiver, aselection of an attribute for comparison from the one or moreattributes; send, using the wireless transceiver and to the server, theselection; receive, using the wireless transceiver, from the server, andbased on the selection, information indicating a path from the locationof the apparatus to a location of the one or more additional vehicles;determine, based on the information indicating the path, one or moredirections from the apparatus to the one or more additional vehicles;determine, based on determining a relative orientation of the apparatusand the one or more additional vehicles, one or more directionindicators corresponding to the one or more directions; and output, fordisplay on the display screen and based on the relative orientation, theone or more direction indicators overlaid on a video of an environmentof the apparatus.
 17. The apparatus of claim 16, wherein the locationsensor comprises a global positioning system (GPS) sensor.
 18. Theapparatus of claim 16, wherein the one or more direction indicatorscomprise a plurality of direction indicators each relative to one of aplurality of vehicles of the one or more additional vehicles.
 19. Theapparatus of claim 16, wherein the one or more direction indicatorscomprises a directional symbol indicating a relative position of one ofthe one or more additional vehicles based on the relative orientation.20. The apparatus of claim 16, wherein the relative orientation is basedon feedback from a solid-state gyroscope.